Apparatus for transmitting broadcast signal, apparatus for receiving broadcast signal, method for transmitting broadcast signal and method for receiving broadcast signal

ABSTRACT

A method of generating and processing a broadcast signal according to an embodiment of the present invention includes: receiving one or more packets, from among Internet protocol (IP) packets and MPEG2-TS packets, as input packets; generating at least one link layer packet including the received input packets, generating a broadcast signal including the at least one link layer packet; and transmitting the broadcast signal.

TECHNICAL FIELD

The present invention relates to an apparatus for transmitting abroadcast signal, an apparatus for receiving a broadcast signal andmethods for transmitting and receiving a broadcast signal.

BACKGROUND ART

As analog broadcast signal transmission comes to an end, varioustechnologies for transmitting/receiving digital broadcast signals arebeing developed. A digital broadcast signal may include a larger amountof video/audio data than an analog broadcast signal and further includevarious types of additional data in addition to the video/audio data.

DISCLOSURE Technical Problem

That is, a digital broadcast system can provide HD (high definition)images, multichannel audio and various additional services. However,data transmission efficiency for transmission of large amounts of data,robustness of transmission/reception networks and network flexibility inconsideration of mobile reception equipment need to be improved fordigital broadcast.

Technical Solution

The present invention proposes a system for effectively supportingfuture broadcast services in an environment supporting future hybridbroadcast using terrestrial broadcast networks and the Internet andrelated signaling methods, as included and roughly described hereinaccording to the purpose of the present invention.

Advantageous Effects

According to the present invention, the amount of data transmittedbetween a transmitter and a receiver of a broadcast system can beefficiently reduced.

According to the present invention, broadcast signals can be efficientlydelivered from the transmitter to the receiver irrespective of aprotocol used in a higher layer of the broadcast system.

DESCRIPTION OF DRAWINGS

The accompanying drawings, which are included to provide a furtherunderstanding of the invention, illustrate embodiments of the inventionand together with the description serve to explain the principle of theinvention.

FIG. 1 illustrates a protocol stack according to an embodiment of thepresent invention.

FIG. 2 illustrates a service discovery procedure according to anembodiment of the present invention.

FIG. 3 illustrates a low level signaling (LLS) table and a service listtable (SLT) according to an embodiment of the present invention.

FIG. 4 illustrates a USBD and an S-TSID delivered through ROUTEaccording to an embodiment of the present invention.

FIG. 5 illustrates a USBD delivered through MMT according to anembodiment of the present invention.

FIG. 6 illustrates a link layer operation according to an embodiment ofthe present invention.

FIG. 7 illustrates a link mapping table (LMT) according to an embodimentof the present invention.

FIG. 8 illustrates data processing in a link layer according to anembodiment of the present invention.

FIG. 9 illustrates an ALP structure and an interface according to anembodiment of the present invention.

FIG. 10 illustrates a format of a link layer packet according to anembodiment of the present invention.

FIG. 11 illustrates a base header structure of a link layer packetaccording to an embodiment of the present invention.

FIG. 12 illustrates a syntax of a link layer packet header according toan embodiment of the present invention.

FIG. 13 illustrates a structure and syntax of an additional header for asingle packet according to an embodiment of the present invention.

FIG. 14 illustrates a structure and syntax of an additional header of alink layer packet in the case of segmentation according to an embodimentof the present invention.

FIG. 15 illustrates a structure and syntax of the additional header ofthe link layer packet in the case of concatenation according to anembodiment of the present invention.

FIG. 16 illustrates a link layer packet including link layer signalingand a syntax of an additional header included therein according to anembodiment of the present invention.

FIG. 17 illustrates a link layer packet including an extended packet(input packet) and syntax of an additional header included thereinaccording to an embodiment of the present invention.

FIG. 18 illustrates a link layer packet including an MPEG2-TS packet andsyntax of a link layer packet header according to an embodiment of thepresent invention.

FIG. 19 illustrates a process of removing null packets from MPEG2-TSpackets according to an embodiment of the present invention.

FIG. 20 illustrates a process of deleting headers from MPEG2-TS packetsaccording to an embodiment of the present invention.

FIG. 21 illustrates a single packet encapsulation structure of a linklayer according to an embodiment of the present invention.

FIG. 22 illustrates a link layer packet encapsulation structure to whichsegmentation is applied according to an embodiment of the presentinvention.

FIG. 23 illustrates a link layer packet encapsulation structure to whichconcatenation is applied according to an embodiment of the presentinvention.

FIG. 24 illustrates the concept of MPEG2-TS packet encapsulation in alink layer according to an embodiment of the present invention.

FIG. 25 illustrates the concept of MPEG2-TS packet encapsulation in thelink layer using null packet removal according to an embodiment of thepresent invention.

FIG. 26 illustrates the concept of MPEG2-TS packet encapsulation in thelink layer using TS header removal according to an embodiment of thepresent invention.

FIG. 27 illustrates a transmission path with respect to context when IPpacket header compression in the link layer is performed according to anembodiment of the present invention.

FIG. 28 illustrates a process of acquiring a context in a receiveraccording to an embodiment of the present invention.

FIG. 29 is a flowchart illustrating a method of generating andprocessing a broadcast signal according to an embodiment of the presentinvention.

FIG. 30 illustrates a broadcast system according to an embodiment of thepresent invention.

BEST MODE

Reference will now be made in detail to the preferred embodiments of thepresent invention, examples of which are illustrated in the accompanyingdrawings. The detailed description, which will be given below withreference to the accompanying drawings, is intended to explain exemplaryembodiments of the present invention, rather than to show the onlyembodiments that can be implemented according to the present invention.The following detailed description includes specific details in order toprovide a thorough understanding of the present invention. However, itwill be apparent to those skilled in the art that the present inventionmay be practiced without such specific details.

Although the terms used in the present invention are selected fromgenerally known and used terms, some of the terms mentioned in thedescription of the present invention have been selected by the applicantat his or her discretion, the detailed meanings of which are describedin relevant parts of the description herein. Furthermore, it is requiredthat the present invention is understood, not simply by the actual termsused but by the meanings of each term lying within.

The present invention provides apparatuses and methods for transmittingand receiving broadcast signals for future broadcast services. Futurebroadcast services according to an embodiment of the present inventioninclude a terrestrial broadcast service, a mobile broadcast service, anultra high definition television (UHDTV) service, etc. The presentinvention may process broadcast signals for the future broadcastservices through non-MIMO (Multiple Input Multiple Output) or MIMOaccording to one embodiment. A non-MIMO scheme according to anembodiment of the present invention may include a MISO (Multiple InputSingle Output) scheme, a SISO (Single Input Single Output) scheme, etc.The present invention proposes a physical profile (or system) optimizedto minimize receiver complexity while accomplishing performance requiredfor a specific purpose.

FIG. 1 is a diagram showing a protocol stack according to an embodimentof the present invention.

A service may be delivered to a receiver through a plurality of layers.First, a transmission side may generate service data. The service datamay be processed for transmission at a delivery layer of thetransmission side and the service data may be encoded into a broadcastsignal and transmitted over a broadcast or broadband network at aphysical layer.

Here, the service data may be generated in an ISO base media file format(BMFF). ISO BMFF media files may be used for broadcast/broadband networkdelivery, media encapsulation and/or synchronization format. Here, theservice data is all data related to the service and may include servicecomponents configuring a linear service, signaling information thereof,non real time (NRT) data and other files.

The delivery layer will be described. The delivery layer may provide afunction for transmitting service data. The service data may bedelivered over a broadcast and/or broadband network.

Broadcast service delivery may include two methods.

As a first method, service data may be processed in media processingunits (MPUs) based on MPEG media transport (MMT) and transmitted usingan MMT protocol (MMTP). In this case, the service data delivered usingthe MMTP may include service components for a linear service and/orservice signaling information thereof.

As a second method, service data may be processed into DASH segments andtransmitted using real time object delivery over unidirectionaltransport (ROUTE), based on MPEG DASH. In this case, the service datadelivered through the ROUTE protocol may include service components fora linear service, service signaling information thereof and/or NRT data.That is, the NRT data and non-timed data such as files may be deliveredthrough ROUTE.

Data processed according to MMTP or ROUTE protocol may be processed intoIP packets through a UDP/IP layer. In service data delivery over thebroadcast network, a service list table (SLT) may also be delivered overthe broadcast network through a UDP/IP layer. The SLT may be deliveredin a low level signaling (LLS) table. The SLT and LLS table will bedescribed later.

IP packets may be processed into link layer packets in a link layer. Thelink layer may encapsulate various formats of data delivered from ahigher layer into link layer packets and then deliver the packets to aphysical layer. The link layer will be described later.

In hybrid service delivery, at least one service element may bedelivered through a broadband path. In hybrid service delivery, datadelivered over broadband may include service components of a DASHformat, service signaling information thereof and/or NRT data. This datamay be processed through HTTP/TCP/IP and delivered to a physical layerfor broadband transmission through a link layer for broadbandtransmission.

The physical layer may process the data received from the delivery layer(higher layer and/or link layer) and transmit the data over thebroadcast or broadband network. A detailed description of the physicallayer will be given later.

The service will be described. The service may be a collection ofservice components displayed to a user, the components may be of variousmedia types, the service may be continuous or intermittent, the servicemay be real time or non real time, and a real-time service may include asequence of TV programs.

The service may have various types. First, the service may be a linearaudio/video or audio service having app based enhancement. Second, theservice may be an app based service, reproduction/configuration of whichis controlled by a downloaded application. Third, the service may be anESG service for providing an electronic service guide (ESG). Fourth, theservice may be an emergency alert (EA) service for providing emergencyalert information.

When a linear service without app based enhancement is delivered overthe broadcast network, the service component may be delivered by (1) oneor more ROUTE sessions or (2) one or more MMTP sessions.

When a linear service having app based enhancement is delivered over thebroadcast network, the service component may be delivered by (1) one ormore ROUTE sessions or (2) zero or more MMTP sessions. In this case,data used for app based enhancement may be delivered through a ROUTEsession in the form of NRT data or other files. In one embodiment of thepresent invention, simultaneous delivery of linear service components(streaming media components) of one service using two protocols may notbe allowed.

When an app based service is delivered over the broadcast network, theservice component may be delivered by one or more ROUTE sessions. Inthis case, the service data used for the app based service may bedelivered through the ROUTE session in the form of NRT data or otherfiles.

Some service components of such a service, some NRT data, files, etc.may be delivered through broadband (hybrid service delivery).

That is, in one embodiment of the present invention, linear servicecomponents of one service may be delivered through the MMT protocol. Inanother embodiment of the present invention, the linear servicecomponents of one service may be delivered through the ROUTE protocol.In another embodiment of the present invention, the linear servicecomponents of one service and NRT data (NRT service components) may bedelivered through the ROUTE protocol. In another embodiment of thepresent invention, the linear service components of one service may bedelivered through the MMT protocol and the NRT data (NRT servicecomponents) may be delivered through the ROUTE protocol. In theabove-described embodiments, some service components of the service orsome NRT data may be delivered through broadband. Here, the app basedservice and data regarding app based enhancement may be delivered overthe broadcast network according to ROUTE or through broadband in theform of NRT data. NRT data may be referred to as locally cached data.

Each ROUTE session includes one or more LCT sessions for wholly orpartially delivering content components configuring the service. Instreaming service delivery, the LCT session may deliver individualcomponents of a user service, such as audio, video or closed captionstream. The streaming media is formatted into a DASH segment.

Each MMTP session includes one or more MMTP packet flows for deliveringall or some of content components or an MMT signaling message. The MMTPpacket flow may deliver a component formatted into MPU or an MMTsignaling message.

For delivery of an NRT user service or system metadata, the LCT sessiondelivers a file based content item. Such content files may includeconsecutive (timed) or discrete (non-timed) media components of the NRTservice or metadata such as service signaling or ESG fragments. Systemmetadata such as service signaling or ESG fragments may be deliveredthrough the signaling message mode of the MMTP.

A receiver may detect a broadcast signal while a tuner tunes tofrequencies. The receiver may extract and send an SLT to a processingmodule. The SLT parser may parse the SLT and acquire and store data in achannel map. The receiver may acquire and deliver bootstrap informationof the SLT to a ROUTE or MMT client. The receiver may acquire and storean SLS. USBD may be acquired and parsed by a signaling parser.

FIG. 2 is a diagram showing a service discovery procedure according toone embodiment of the present invention.

A broadcast stream delivered by a broadcast signal frame of a physicallayer may carry low level signaling (LLS). LLS data may be carriedthrough payload of IP packets delivered to a well-known IP address/port.This LLS may include an SLT according to type thereof. The LLS data maybe formatted in the form of an LLS table. A first byte of every UDP/IPpacket carrying the LLS data may be the start of the LLS table. Unlikethe shown embodiment, an IP stream for delivering the LLS data may bedelivered to a PLP along with other service data.

The SLT may enable the receiver to generate a service list through fastchannel scan and provides access information for locating the SLS. TheSLT includes bootstrap information. This bootstrap information mayenable the receiver to acquire service layer signaling (SLS) of eachservice. When the SLS, that is, service signaling information, isdelivered through ROUTE, the bootstrap information may include an LCTchannel carrying the SLS, a destination IP address of a ROUTE sessionincluding the LCT channel and destination port information. When the SLSis delivered through the MMT, the bootstrap information may include adestination IP address of an MMTP session carrying the SLS anddestination port information.

In the shown embodiment, the SLS of service #1 described in the SLT isdelivered through ROUTE and the SLT may include bootstrap informationsIP1, dIP1 and dPort1 of the ROUTE session including the LCT channeldelivered by the SLS. The SLS of service #2 described in the SLT isdelivered through MMT and the SLT may include bootstrap informationsIP2, dIP2 and dPort2 of the MMTP session including the MMTP packet flowdelivered by the SLS.

The SLS is signaling information describing the properties of theservice and may include receiver capability information forsignificantly reproducing the service or providing information foracquiring the service and the service component of the service. Wheneach service has separate service signaling, the receiver acquiresappropriate SLS for a desired service without parsing all SLSs deliveredwithin a broadcast stream.

When the SLS is delivered through the ROUTE protocol, the SLS may bedelivered through a dedicated LCT channel of a ROUTE session indicatedby the SLT. In some embodiments, this LCT channel may be an LCT channelidentified by tsi=0. In this case, the SLS may include a user servicebundle description (USBD)/user service description (USD), service-basedtransport session instance description (S-TSID) and/or mediapresentation description (MPD).

Here, USBD/USD is one of SLS fragments and may serve as a signaling hubdescribing detailed description information of a service. The USBD mayinclude service identification information, device capabilityinformation, etc. The USBD may include reference information (URIreference) of other SLS fragments (S-TSID, MPD, etc.). That is, theUSBD/USD may reference the S-TSID and the MPD. In addition, the USBD mayfurther include metadata information for enabling the receiver to decidea transmission mode (broadcast/broadband network). A detaileddescription of the USBD/USD will be given below.

The S-TSID is one of SLS fragments and may provide overall sessiondescription information of a transport session carrying the servicecomponent of the service. The S-TSID may provide the ROUTE sessionthrough which the service component of the service is delivered and/ortransport session description information for the LCT channel of theROUTE session. The S-TSID may provide component acquisition informationof service components associated with one service. The S-TSID mayprovide mapping between DASH representation of the MPD and the tsi ofthe service component. The component acquisition information of theS-TSID may be provided in the form of the identifier of the associatedDASH representation and tsi and may or may not include a PLP ID in someembodiments. Through the component acquisition information, the receivermay collect audio/video components of one service and perform bufferingand decoding of DASH media segments. The S-TSID may be referenced by theUSBD as described above. A detailed description of the S-TSID will begiven below.

The MPD is one of SLS fragments and may provide a description of DASHmedia presentation of the service. The MPD may provide a resourceidentifier of media segments and provide context information within themedia presentation of the identified resources. The MPD may describeDASH representation (service component) delivered over the broadcastnetwork and describe additional DASH presentation delivered overbroadband (hybrid delivery). The MPD may be referenced by the USBD asdescribed above.

When the SLS is delivered through the MMT protocol, the SLS may bedelivered through a dedicated MMTP packet flow of the MMTP sessionindicated by the SLT. In some embodiments, the packet_id of the MMTPpackets delivering the SLS may have a value of 00. In this case, the SLSmay include a USBD/USD and/or MMT packet (MP) table.

Here, the USBD is one of SLS fragments and may describe detaileddescription information of a service as in ROUTE. This USBD may includereference information (URI information) of other SLS fragments. The USBDof the MMT may reference an MP table of MMT signaling. In someembodiments, the USBD of the MMT may include reference information ofthe S-TSID and/or the MPD. Here, the S-TSID is for NRT data deliveredthrough the ROUTE protocol. Even when a linear service component isdelivered through the MMT protocol, NRT data may be delivered via theROUTE protocol. The MPD is for a service component delivered overbroadband in hybrid service delivery. The detailed description of theUSBD of the MMT will be given below.

The MP table is a signaling message of the MMT for MPU components andmay provide overall session description information of an MMTP sessioncarrying the service component of the service. In addition, the MP tablemay include a description of an asset delivered through the MMTPsession. The MP table is streaming signaling information for MPUcomponents and may provide a list of assets corresponding to one serviceand location information (component acquisition information) of thesecomponents. The detailed description of the MP table may be defined inthe MMT or modified. Here, the asset is a multimedia data entity, iscombined by one unique ID, and may mean a data entity used to onemultimedia presentation. The asset may correspond to service componentsconfiguring one service. A streaming service component (MPU)corresponding to a desired service may be accessed using the MP table.The MP table may be referenced by the USBD as described above.

The other MMT signaling messages may be defined. Additional informationassociated with the service and the MMTP session may be described bysuch MMT signaling messages.

The ROUTE session is identified by a source IP address, a destination IPaddress and a destination port number. The LCT session is identified bya unique transport session identifier (TSI) within the range of a parentROUTE session. The MMTP session is identified by a destination IPaddress and a destination port number. The MMTP packet flow isidentified by a unique packet_id within the range of a parent MMTPsession.

In case of ROUTE, the S-TSID, the USBD/USD, the MPD or the LCT sessiondelivering the same may be referred to as a service signaling channel.In case of MMTP, the USBD/UD, the MMT signaling message or the packetflow delivering the same may be referred to as a service signalingchannel.

Unlike the shown embodiment, one ROUTE or MMTP session may be deliveredover a plurality of PLPs. That is, one service may be delivered throughone or more PLPs. Unlike the shown embodiment, in some embodiments,components configuring one service may be delivered through differentROUTE sessions. In addition, in some embodiments, components configuringone service may be delivered through different MMTP sessions. In someembodiments, components configuring one service may be divided anddelivered in a ROUTE session and an MMTP session. Although not shown,components configuring one service may be delivered through broadband(hybrid delivery).

FIG. 3 is a diagram showing a low level signaling (LLS) table and aservice list table (SLT) according to one embodiment of the presentinvention.

One embodiment t3010 of the LLS table may include information accordingto an LLS_table_id field, a provider_id field, an LLS_table_versionfield and/or an LLS_table_id field.

The LLS_table_id field may identify the type of the LLS table, and theprovider_id field may identify a service provider associated withservices signaled by the LLS table. Here, the service provider is abroadcaster using all or some of the broadcast streams and theprovider_id field may identify one of a plurality of broadcasters whichis using the broadcast streams. The LLS_table_version field may providethe version information of the LLS table.

According to the value of the LLS_table_id field, the LLS table mayinclude one of the above-described SLT, a rating region table (RRT)including information on a content advisory rating, SystemTimeinformation for providing information associated with a system time, acommon alert protocol (CAP) message for providing information associatedwith emergency alert. In some embodiments, the other information may beincluded in the LLS table.

One embodiment t3020 of the shown SLT may include an @bsid attribute, an@sltCapabilities attribute, an sltInetUrl element and/or a Serviceelement. Each field may be omitted according to the value of the shownUse column or a plurality of fields may be present.

The @bsid attribute may be the identifier of a broadcast stream. The@sltCapabilities attribute may provide capability information requiredto decode and significantly reproduce all services described in the SLT.The sltInetUrl element may provide base URL information used to obtainservice signaling information and ESG for the services of the SLT overbroadband. The sltInetUrl element may further include an @urlTypeattribute, which may indicate the type of data capable of being obtainedthrough the URL.

The Service element may include information on services described in theSLT, and the Service element of each service may be present. The Serviceelement may include an @serviceId attribute, an @sltSvcSeqNum attribute,an @protected attribute, an @majorChannelNo attribute, an@minorChannelNo attribute, an @serviceCategory attribute, an@shortServiceName attribute, an @hidden attribute, an@broadbandAccessRequired attribute, an @svcCapabilities attribute, aBroadcastSvcSignaling element and/or an svcInetUrl element.

The @serviceId attribute is the identifier of the service and the@sltSvcSeqNum attribute may indicate the sequence number of the SLTinformation of the service. The @protected attribute may indicatewhether at least one service component necessary for significantreproduction of the service is protected. The @majorChannelNo attributeand the @minorChannelNo attribute may indicate the major channel numberand minor channel number of the service, respectively.

The @serviceCategory attribute may indicate the category of the service.The category of the service may include a linear A/V service, a linearaudio service, an app based service, an ESG service, an EAS service,etc. The @shortServiceName attribute may provide the short name of theservice. The @hidden attribute may indicate whether the service is fortesting or proprietary use. The @broadbandAccessRequired attribute mayindicate whether broadband access is necessary for significantreproduction of the service. The @svcCapabilities attribute may providecapability information necessary for decoding and significantreproduction of the service.

The BroadcastSvcSignaling element may provide information associatedwith broadcast signaling of the service. This element may provideinformation such as location, protocol and address with respect tosignaling over the broadcast network of the service. Details thereofwill be described below.

The svcInetUrl element may provide URL information for accessing thesignaling information of the service over broadband. The sltInetUrlelement may further include an @urlType attribute, which may indicatethe type of data capable of being obtained through the URL.

The above-described BroadcastSvcSignaling element may include an@slsProtocol attribute, an @slsMajorProtocolVersion attribute, an@slsMinorProtocolVersion attribute, an @slsPlpId attribute, an@slsDestinationIpAddress attribute, an @slsDestinationUdpPort attributeand/or an @slsSourceIpAddress attribute.

The @slsProtocol attribute may indicate the protocol used to deliver theSLS of the service (ROUTE, MMT, etc.). The @slsMajorProtocolVersionattribute and the @slsMinorProtocolVersion attribute may indicate themajor version number and minor version number of the protocol used todeliver the SLS of the service, respectively.

The @slsPlpId attribute may provide a PLP identifier for identifying thePLP delivering the SLS of the service. In some embodiments, this fieldmay be omitted and the PLP information delivered by the SLS may bechecked using a combination of the information of the below-describedLMT and the bootstrap information of the SLT.

The @slsDestinationIpAddress attribute, the @slsDestinationUdpPortattribute and the @slsSourceIpAddress attribute may indicate thedestination IP address, destination UDP port and source IP address ofthe transport packets delivering the SLS of the service, respectively.These may identify the transport session (ROUTE session or MMTP session)delivered by the SLS. These may be included in the bootstrapinformation.

FIG. 4 is a diagram showing a USBD and an S-TSID delivered through ROUTEaccording to one embodiment of the present invention.

One embodiment t4010 of the shown USBD may have a bundleDescription rootelement. The bundleDescription root element may have auserServiceDescription element. The userServiceDescription element maybe an instance of one service.

The userServiceDescription element may include an @globalServiceIDattribute, an @serviceId attribute, an @serviceStatus attribute, an@fullMPDUri attribute, an @sTSIDUri attribute, a name element, aserviceLanguage element, a capabilityCode element and/or adeliveryMethod element. Each field may be omitted according to the valueof the shown Use column or a plurality of fields may be present.

The @globalServiceID attribute is the globally unique identifier of theservice and may be used for link with ESG data(Service@globalServiceID). The @serviceId attribute is a referencecorresponding to the service entry of the SLT and may be equal to theservice ID information of the SLT. The @serviceStatus attribute mayindicate the status of the service. This field may indicate whether theservice is active or inactive.

The @fullMPDUri attribute may reference the MPD fragment of the service.The MPD may provide a reproduction description of a service componentdelivered over the broadcast or broadband network as described above.The @sTSIDUri attribute may reference the S-TSID fragment of theservice. The S-TSID may provide parameters associated with access to thetransport session carrying the service as described above.

The name element may provide the name of the service. This element mayfurther include an @lang attribute and this field may indicate thelanguage of the name provided by the name element. The serviceLanguageelement may indicate available languages of the service. That is, thiselement may arrange the languages capable of being provided by theservice.

The capabilityCode element may indicate capability or capability groupinformation of a receiver necessary to significantly reproduce theservice. This information is compatible with capability informationformat provided in service announcement.

The deliveryMethod element may provide transmission related informationwith respect to content accessed over the broadcast or broadband networkof the service. The deliveryMethod element may include abroadcastAppService element and/or a unicastAppService element. Each ofthese elements may have a basePattern element as a sub element.

The broadcastAppService element may include transmission associatedinformation of the DASH representation delivered over the broadcastnetwork. The DASH representation may include media components over allperiods of the service presentation.

The basePattern element of this element may indicate a character patternused for the receiver to perform matching with the segment URL. This maybe used for a DASH client to request the segments of the representation.Matching may imply delivery of the media segment over the broadcastnetwork.

The unicastAppService element may include transmission relatedinformation of the DASH representation delivered over broadband. TheDASH representation may include media components over all periods of theservice media presentation.

The basePattern element of this element may indicate a character patternused for the receiver to perform matching with the segment URL. This maybe used for a DASH client to request the segments of the representation.Matching may imply delivery of the media segment over broadband.

One embodiment t4020 of the shown S-TSID may have an S-TSID rootelement. The S-TSID root element may include an @serviceId attributeand/or an RS element. Each field may be omitted according to the valueof the shown Use column or a plurality of fields may be present.

The @serviceId attribute is the identifier of the service and mayreference the service of the USBD/USD. The RS element may describeinformation on ROUTE sessions through which the service components ofthe service are delivered. According to the number of ROUTE sessions, aplurality of elements may be present. The RS element may further includean @bsid attribute, an @sIpAddr attribute, an @dIpAddr attribute, an@dport attribute, an @PLPID attribute and/or an LS element.

The @bsid attribute may be the identifier of a broadcast stream in whichthe service components of the service are delivered. If this field isomitted, a default broadcast stream may be a broadcast stream includingthe PLP delivering the SLS of the service. The value of this field maybe equal to that of the @bsid attribute.

The @sIpAddr attribute, the @dIpAddr attribute and the @dport attributemay indicate the source IP address, destination IP address anddestination UDP port of the ROUTE session, respectively. When thesefields are omitted, the default values may be the source address,destination IP address and destination UDP port values of the currentROUTE session delivering the SLS, that is, the S-TSID. This field maynot be omitted in another ROUTE session delivering the servicecomponents of the service, not in the current ROUTE session.

The @PLPID attribute may indicate the PLP ID information of the ROUTEsession. If this field is omitted, the default value may be the PLP IDvalue of the current PLP delivered by the S-TSID. In some embodiments,this field is omitted and the PLP ID information of the ROUTE sessionmay be checked using a combination of the information of thebelow-described LMT and the IP address/UDP port information of the RSelement.

The LS element may describe information on LCT channels through whichthe service components of the service are transmitted. According to thenumber of LCT channel, a plurality of elements may be present. The LSelement may include an @tsi attribute, an @PLPID attribute, an @bwattribute, an @startTime attribute, an @endTime attribute, a SrcFlowelement and/or a RepairFlow element.

The @tsi attribute may indicate the tsi information of the LCT channel.Using this, the LCT channels through which the service components of theservice are delivered may be identified. The @PLPID attribute mayindicate the PLP ID information of the LCT channel. In some embodiments,this field may be omitted. The @bw attribute may indicate the maximumbandwidth of the LCT channel. The @startTime attribute may indicate thestart time of the LCT session and the @endTime attribute may indicatethe end time of the LCT channel.

The SrcFlow element may describe the source flow of ROUTE. The sourceprotocol of ROUTE is used to transmit a delivery object and at least onesource flow may be established within one ROUTE session. The source flowmay deliver associated objects as an object flow.

The RepairFlow element may describe the repair flow of ROUTE. Deliveryobjects delivered according to the source protocol may be protectedaccording to forward error correction (FEC) and the repair protocol maydefine an FEC framework enabling FEC protection.

FIG. 5 is a diagram showing a USBD delivered through MMT according toone embodiment of the present invention.

One embodiment of the shown USBD may have a bundleDescription rootelement. The bundleDescription root element may have auserServiceDescription element. The userServiceDescription element maybe an instance of one service.

The userServiceDescription element may include an @globalServiceIDattribute, an @serviceId attribute, a Name element, a serviceLanguageelement, a contentAdvisoryRating element, a Channel element, ampuComponent element, a routeComponent element, a broadbandComponentelement and/or a ComponentInfo element. Each field may be omittedaccording to the value of the shown Use column or a plurality of fieldsmay be present.

The @globalServiceID attribute, the @serviceId attribute, the Nameelement and/or the serviceLanguage element may be equal to the fields ofthe USBD delivered through ROUTE. The contentAdvisoryRating element mayindicate the content advisory rating of the service. This information iscompatible with content advisory rating information format provided inservice announcement. The Channel element may include informationassociated with the service. A detailed description of this element willbe given below.

The mpuComponent element may provide a description of service componentsdelivered as the MPU of the service. This element may further include an@mmtPackageId attribute and/or an @nextMmtPackageId attribute. The@mmtPackageId attribute may reference the MMT package of the servicecomponents delivered as the MPU of the service. The @nextMmtPackageIdattribute may reference an MMT package to be used after the MMT packagereferenced by the @mmtPackageId attribute in terms of time. Through theinformation of this element, the MP table may be referenced.

The routeComponent element may include a description of the servicecomponents of the service. Even when linear service components aredelivered through the MMT protocol, NRT data may be delivered accordingto the ROUTE protocol as described above. This element may describeinformation on such NRT data. A detailed description of this elementwill be given below.

The broadbandComponent element may include the description of theservice components of the service delivered over broadband. In hybridservice delivery, some service components of one service or other filesmay be delivered over broadband. This element may describe informationon such data. This element may further an @fullMPDUri attribute. Thisattribute may reference the MPD describing the service componentdelivered over broadband. In addition to hybrid service delivery, thebroadcast signal may be weakened due to traveling in a tunnel and thusthis element may be necessary to support handoff between broadband andbroadband. When the broadcast signal is weak, the service component isacquired over broadband and, when the broadcast signal becomes strong,the service component is acquired over the broadcast network to secureservice continuity.

The ComponentInfo element may include information on the servicecomponents of the service. According to the number of service componentsof the service, a plurality of elements may be present. This element maydescribe the type, role, name, identifier or protection of each servicecomponent. Detailed information of this element will be described below.

The above-described Channel element may further include an @serviceGenreattribute, an @serviceIcon attribute and/or a ServiceDescriptionelement. The @serviceGenre attribute may indicate the genre of theservice and the @serviceIcon attribute may include the URL informationof the representative icon of the service. The ServiceDescriptionelement may provide the service description of the service and thiselement may further include an @serviceDescrText attribute and/or an@serviceDescrLang attribute. These attributes may indicate the text ofthe service description and the language used in the text.

The above-described routeComponent element may further include an@sTSIDUri attribute, an @sTSIDDestinationIpAddress attribute, an@sTSIDDestinationUdpPort attribute, an @sTSIDSourceIpAddress attribute,an @sTSIDMajorProtocolVersion attribute and/or an@sTSIDMinorProtocolVersion attribute.

The @sTSIDUri attribute may reference an S-TSID fragment. This field maybe equal to the field of the USBD delivered through ROUTE. This S-TSIDmay provide access related information of the service componentsdelivered through ROUTE. This S-TSID may be present for NRT datadelivered according to the ROUTE protocol in a state of deliveringlinear service component according to the MMT protocol.

The @sTSIDDestinationIpAddress attribute, the @sTSIDDestinationUdpPortattribute and the @sTSIDSourceIpAddress attribute may indicate thedestination IP address, destination UDP port and source IP address ofthe transport packets carrying the above-described S-TSID. That is,these fields may identify the transport session (MMTP session or theROUTE session) carrying the above-described S-TSID.

The @sTSIDMajorProtocolVersion attribute and the@sTSIDMinorProtocolVersion attribute may indicate the major versionnumber and minor version number of the transport protocol used todeliver the above-described S-TSID, respectively.

The above-described ComponentInfo element may further include an@componentType attribute, an @componentRole attribute, an@componentProtectedFlag attribute, an @componentId attribute and/or an@componentName attribute.

The @componentType attribute may indicate the type of the component. Forexample, this attribute may indicate whether the component is an audio,video or closed caption component. The @componentRole attribute mayindicate the role of the component. For example, this attribute mayindicate main audio, music, commentary, etc. if the component is anaudio component. This attribute may indicate primary video if thecomponent is a video component. This attribute may indicate a normalcaption or an easy reader type if the component is a closed captioncomponent.

The @componentProtectedFlag attribute may indicate whether the servicecomponent is protected, for example, encrypted. The @componentIdattribute may indicate the identifier of the service component. Thevalue of this attribute may be the asset_id (asset ID) of the MP tablecorresponding to this service component. The @componentName attributemay indicate the name of the service component.

FIG. 6 is a diagram showing link layer operation according to oneembodiment of the present invention.

The link layer may be a layer between a physical layer and a networklayer. A transmission side may transmit data from the network layer tothe physical layer and a reception side may transmit data from thephysical layer to the network layer (t6010). The purpose of the linklayer is to compress (abstract) all input packet types into one formatfor processing by the physical layer and to secure flexibility andexpandability of an input packet type which is not defined yet. Inaddition, the link layer may provide option for compressing(abstracting) unnecessary information of the header of input packets toefficiently transmit input data. Operation such as overhead reduction,encapsulation, etc. of the link layer is referred to as a link layerprotocol and packets generated using this protocol may be referred to aslink layer packets. The link layer may perform functions such as packetencapsulation, overhead reduction and/or signaling transmission.

At the transmission side, the link layer (ALP) may perform an overheadreduction procedure with respect to input packets and then encapsulatethe input packets into link layer packets. In addition, in someembodiments, the link layer may perform encapsulation into the linklayer packets without performing the overhead reduction procedure. Dueto use of the link layer protocol, data transmission overhead on thephysical layer may be significantly reduced and the link layer protocolaccording to the present invention may provide IP overhead reductionand/or MPEG-2 TS overhead reduction.

When the shown IP packets are input as input packets (t6010), the linklayer may sequentially perform IP header compression, adaptation and/orencapsulation. In some embodiments, some processes may be omitted. Forexample, the RoHC module may perform IP packet header compression toreduce unnecessary overhead. Context information may be extractedthrough the adaptation procedure and transmitted out of band. The IPheader compression and adaption procedure may be collectively referredto as IP header compression. Thereafter, the IP packets may beencapsulated into link layer packets through the encapsulationprocedure.

When MPEG 2 TS packets are input as input packets, the link layer maysequentially perform overhead reduction and/or an encapsulationprocedure with respect to the TS packets. In some embodiments, someprocedures may be omitted. In overhead reduction, the link layer mayprovide sync byte removal, null packet deletion and/or common headerremoval (compression). Through sync byte removal, overhead reduction of1 byte may be provided per TS packet. Null packet deletion may beperformed in a manner in which reinsertion is possible at the receptionside. In addition, deletion (compression) may be performed in a mannerin which common information between consecutive headers may be restoredat the reception side. Some of the overhead reduction procedures may beomitted. Thereafter, through the encapsulation procedure, the TS packetsmay be encapsulated into link layer packets. The link layer packetstructure for encapsulation of the TS packets may be different from thatof the other types of packets.

First, IP header compression will be described.

The IP packets may have a fixed header format but some informationnecessary for a communication environment may be unnecessary for abroadcast environment. The link layer protocol may compress the headerof the IP packet to provide a mechanism for reducing broadcast overhead.

IP header compression may employ a header compressor/decompressor and/oran adaptation module. The IP header compressor (RoHC compressor) mayreduce the size of each IP packet header based on the RoHC scheme.Thereafter, the adaptation module may extract context information andgenerate signaling information from each packet stream. A receiver mayparse signaling information associated with the packet stream and attachcontext information to the packet stream. The RoHC decompressor mayrestore the packet header to reconfigure an original IP packet.Hereinafter, IP header compression may mean only IP header compressionby a header compression or a combination of IP header compression and anadaptation process by an adaptation module. The same is true indecompressing.

Hereinafter, adaptation will be described.

In transmission of a single-direction link, when the receiver does nothave context information, the decompressor cannot restore the receivedpacket header until complete context is received. This may lead tochannel change delay and turn-on delay. Accordingly, through theadaptation function, configuration parameters and context informationbetween the compressor and the decompressor may be transmitted out ofband. The adaptation function may provide construction of link layersignaling using context information and/or configuration parameters. Theadaptation function may use previous configuration parameters and/orcontext information to periodically transmit link layer signalingthrough each physical frame.

Context information is extracted from the compressed IP packets andvarious methods may be used according to adaptation mode.

Mode #1 refers to a mode in which no operation is performed with respectto the compressed packet stream and an adaptation module operates as abuffer.

Mode #2 refers to a mode in which an IR packet is detected from acompressed packet stream to extract context information (static chain).After extraction, the IR packet is converted into an IR-DYN packet andthe IR-DYN packet may be transmitted in the same order within the packetstream in place of an original IR packet.

Mode #3 (t6020) refers to a mode in which IR and IR-DYN packets aredetected from a compressed packet stream to extract context information.A static chain and a dynamic chain may be extracted from the IR packetand a dynamic chain may be extracted from the IR-DYN packet. Afterextraction, the IR and IR-DYN packets are converted into normalcompression packets. The converted packets may be transmitted in thesame order within the packet stream in place of original IR and IR-DYNpackets.

In each mode, the context information is extracted and the remainingpackets may be encapsulated and transmitted according to the link layerpacket structure for the compressed IP packets. The context informationmay be encapsulated and transmitted according to the link layer packetstructure for signaling information, as link layer signaling.

The extracted context information may be included in a RoHC-Udescription table (RDT) and may be transmitted separately from the RoHCpacket flow. Context information may be transmitted through a specificphysical data path along with other signaling information. The specificphysical data path may mean one of normal PLPs, a PLP in which low levelsignaling (LLS) is delivered, a dedicated PLP or an L1 signaling path.Here, the RDT may be context information (static chain and/or dynamicchain) and/or signaling information including information associatedwith header compression. In some embodiments, the RDT shall betransmitted whenever the context information is changed. In addition, insome embodiments, the RDT shall be transmitted every physical frame. Inorder to transmit the RDT every physical frame, the previous RDT may bereused.

The receiver may select a first PLP and first acquire signalinginformation of the SLT, the RDT, the LMT, etc., prior to acquisition ofa packet stream. When signaling information is acquired, the receivermay combine the signaling information to acquire mapping betweenservice—IP information—context information—PLP. That is, the receivermay check which service is transmitted in which IP streams or which IPstreams are delivered in which PLP and acquire context information ofthe PLPs. The receiver may select and decode a PLP carrying a specificpacket stream. The adaptation module may parse context information andcombine the context information with the compressed packets. To thisend, the packet stream may be restored and delivered to the RoHCdecompressor. Thereafter, decompression may start. At this time, thereceiver may detect IR packets to start decompression from an initiallyreceived IR packet (mode 1), detect IR-DYN packets to startdecompression from an initially received IR-DYN packet (mode 2) or startdecompression from any compressed packet (mode 3).

Hereinafter, packet encapsulation will be described.

The link layer protocol may encapsulate all types of input packets suchas IP packets, TS packets, etc. into link layer packets. To this end,the physical layer processes only one packet format independently of theprotocol type of the network layer (here, an MPEG-2 TS packet isconsidered as a network layer packet). Each network layer packet orinput packet is modified into the payload of a generic link layerpacket.

In the packet encapsulation procedure, segmentation may be used. If thenetwork layer packet is too large to be processed in the physical layer,the network layer packet may be segmented into two or more segments. Thelink layer packet header may include fields for segmentation of thetransmission side and recombination of the reception side. Each segmentmay be encapsulated into the link layer packet in the same order as theoriginal location.

In the packet encapsulation procedure, concatenation may also be used.If the network layer packet is sufficiently small such that the payloadof the link layer packet includes several network layer packets,concatenation may be performed. The link layer packet header may includefields for performing concatenation. In concatenation, the input packetsmay be encapsulated into the payload of the link layer packet in thesame order as the original input order.

The link layer packet may include a header and a payload. The header mayinclude a base header, an additional header and/or an optional header.The additional header may be further added according to situation suchas concatenation or segmentation and the additional header may includefields suitable for situations. In addition, for delivery of theadditional information, the optional header may be further included.Each header structure may be pre-defined. As described above, if theinput packets are TS packets, a link layer header having packetsdifferent from the other packets may be used.

Hereinafter, link layer signaling will be described.

Link layer signaling may operate at a level lower than that of the IPlayer. The reception side may acquire link layer signaling faster thanIP level signaling of the LLS, the SLT, the SLS, etc. Accordingly, linklayer signaling may be acquired before session establishment.

Link layer signaling may include internal link layer signaling andexternal link layer signaling. Internal link layer signaling may besignaling information generated at the link layer. This includes theabove-described RDT or the below-described LMT. External link layersignaling may be signaling information received from an external module,an external protocol or a higher layer. The link layer may encapsulatelink layer signaling into a link layer packet and deliver the link layerpacket. A link layer packet structure (header structure) for link layersignaling may be defined and link layer signaling information may beencapsulated according to this structure.

FIG. 7 is a diagram showing a link mapping table (LMT) according to oneembodiment of the present invention.

The LMT may provide a list of higher layer sessions carried through thePLP. In addition, the LMT may provide additional information forprocessing link layer packets carrying the higher layer sessions. Here,the higher layer session may also be referred to as multicast.Information on IP streams or transport sessions transmitted through aspecific PLP may be acquired through the LMT. In contrast, informationon through which PLP a specific transport session is delivered may beacquired.

The LMT may be delivered in any PLP identified as carrying LLS. Here,the PLP in which the LLS is delivered may be identified by an LLS flagof L1 detail signaling information of a physical layer. The LLS flag maybe a flag field indicating whether the LLS is delivered in the PLP, eachPLP. Here, L1 detail signaling information may correspond to thebelow-described PLS2 data.

That is, the LMT may be delivered in the same PLP along with the LLS.Each LMT shall describe mapping between PLPs and IP addresses/ports asdescribed above. As described above, the LLS may include an SLT and theIP address/port described in the LMT may be any IP address/portassociated with any service described in the SLT delivered in the samePLP as the LMT.

In some embodiments, the PLP identifier information in theabove-described SLT, SLS, etc. may be used to confirm informationindicating through which PLP a specific transport session indicated bythe SLT or SLS is transmitted may be confirmed.

In another embodiment, the PLP identifier information in theabove-described SLT, SLS, etc. will be omitted and PLP information ofthe specific transport session indicated by the SLT or SLS may beconfirmed by referring to the information in the LMT. In this case, thereceiver may combine the LMT and other IP level signaling information toidentify the PLP. Even in this embodiment, the PLP information in theSLT, SLS, etc. is not omitted and may remain in the SLT, SLS, etc.

The LMT according to the shown embodiment may include a signaling_typefield, a PLP_ID field, a num_session field and/or information on eachsession. Although the LMT of the shown embodiment describes IP streamstransmitted through one PLP, a PLP loop may be added to the LMT todescribe information on a plurality of PLPs in some embodiments. In thiscase, the LMT may describe, in a PLP loop, PLPs for any IP address/portassociated with any service described in the SLT delivered together, asdescribed above.

The signaling_type field may indicate the type of signaling informationdelivered by the table. The value of signaling_type field for the LMTmay be set to 0x01. The signaling_type field may be omitted. The PLP_IDfield may identify a target PLP to be described. If the PLP loop isused, each PLP_ID field may identify each target PLP. The PLP_ID fieldand subsequent fields thereof may be included in the PLP loop. Thebelow-described PLP_ID field is an identifier for one PLP of the PLPloop and the below-described fields may be fields for the correspondingPLP.

The num_session field may indicate the number of higher layer sessionsdelivered through the PLP identified by the corresponding PLP_ID field.According to the number indicated by the num_session field, informationon each session may be included. This information may include asrc_IP_add field, a dst_IP_add field, a src_UDP_port field, adst_UDP_port field, an SID_flag field, a compressed_flag field, an SIDfield and/or a context_id field.

The src_IP_add field, the dst_IP_add field, the src_UDP_port field andthe dst_UDP_port field may indicate the source IP address, thedestination IP address, the source UDP port and the destination UDP portof the transport session among the higher layer sessions deliveredthrough the PLP identified by the corresponding PLP_ID field.

The SID_flag field may indicate whether the link layer packet deliveringthe transport session has an SID field in the optional header. The linklayer packet delivering the higher layer session may have an SID fieldin the optional header and the SID field value may be equal to that ofthe SID field in the LMT.

The compressed_flag field may indicate whether header compression isapplied to the data of the link layer packet delivering the transportsession. In addition, presence/absence of the below-described context_idfield may be determined according to the value of this field. If headercompression is applied (compressed_flag=1), the RDT may be present andthe PLP ID field of the RDT may have the same value as the PLP_ID fieldassociated with this compressed_flag field.

The SID field may indicate the SIDs (sub stream IDs) of the link layerpackets delivering the transport session. These link layer packets mayinclude SIDs having the same values as this SID field in the optionalheader thereof. To this end, the receiver may filter link layer packetsusing LMT information and the SID information of the link layer packetheader, without parsing all link layer packets.

The context_id field may provide a reference for a context id (CID) inthe RDT. The CID information of the RDT may indicate the context ID ofthe compression IP packet stream. The RDT may provide contextinformation of the compression IP packet stream. Through this field, theRDT and the LMT may be associated.

In the above-described embodiments of the signaling information/table ofthe present invention, the fields, elements or attributes may be omittedor may be replaced with other fields. In some embodiments, additionalfields, elements or attributes may be added.

In one embodiment of the present invention, service components of oneservice may be delivered through a plurality of ROUTE sessions. In thiscase, an SLS may be acquired through bootstrap information of an SLT. AnS-TSID and an MPD may be referenced through the USBD of the SLS. TheS-TSID may describe not only the ROUTE session delivered by the SLS butalso transport session description information of another ROUTE sessioncarried by the service components. To this end, the service componentsdelivered through the plurality of ROUTE sessions may all be collected.This is similarly applicable to the case in which the service componentsof one service are delivered through a plurality of MMTP sessions. Forreference, one service component may be simultaneously used by theplurality of services.

In another embodiment of the present invention, bootstrapping of an ESGservice may be performed by a broadcast or broadband network. Byacquiring the ESG over broadband, URL information of the SLT may beused. ESG information may be requested using this URL.

In another embodiment of the present invention, one service component ofone service may be delivered over the broadcast network and the otherservice component may be delivered over broadband (hybrid). The S-TSIDmay describe components delivered over the broadcast network such thatthe ROUTE client acquires desired service components. In addition, theUSBD may have base pattern information to describe which segments (whichcomponents) are delivered through which path. Accordingly, the receivercan confirm a segment to be requested from the broadband service and asegment to be detected in a broadcast stream.

In another embodiment of the present invention, scalable coding of aservice may be performed. The USBD may have all capability informationnecessary to render the service. For example, when one service isprovided in HD or UHD, the capability information of the USBD may have avalue of “HD or UHD”. The receiver may check which component isreproduced in order to render the UHD or HD service using the MPD.

In another embodiment of the present invention, through a TOI field ofthe LCT packets delivered through the LCT channel delivering the SLS,which SLS fragment is delivered using the LCT packets (USBD, S-TSID,MPD, etc.) may be identified.

In another embodiment of the present invention, app components to beused for app based enhancement/an app based service may be deliveredover the broadcast network as NRT components or may be delivered overbroadband. In addition, app signaling for app based enhancement may beperformed by an application signaling table (AST) delivered along withthe SLS. In addition, an event which is signaling for operation to beperformed by the app may be delivered in the form of an event messagetable (EMT) along with the SLS, may be signaled in the MPD or may bein-band signaled in the form of a box within DASH representation. TheAST, the EMT, etc. may be delivered over broadband. App basedenhancement, etc. may be provided using the collected app components andsuch signaling information.

In another embodiment of the present invention, a CAP message may beincluded and provided in the above-described LLS table for emergencyalert. Rich media content for emergency alert may also be provided. Richmedia may be signaled by a CAP message and, if rich media is present,the rich media may be provided as an EAS service signaled by the SLT.

In another embodiment of the present invention, linear servicecomponents may be delivered over the broadcast network according to theMMT protocol. In this case, NRT data (e.g., app components) of theservice may be delivered over the broadcast network according to theROUTE protocol. In addition, the data of the service may be deliveredover broadband. The receiver may access the MMTP session delivering theSLS using the bootstrap information of the SLT. The USBD of the SLSaccording to the MMT may reference the MP table such that the receiveracquires linear service components formatted into the MPU deliveredaccording to the MMT protocol. In addition, the USBD may furtherreference the S-TSID such that the receiver acquires NRT data deliveredaccording to the ROUTE protocol. In addition, the USBD may furtherreference the MPD to provide a reproduction description of datadelivered over broadband.

In another embodiment of the present invention, the receiver may deliverlocation URL information capable of acquiring a file content item (file,etc.) and/or a streaming component to a companion device through a websocket method. The application of the companion device may acquirecomponents, data, etc. through a request through HTTP GET using thisURL. In addition, the receiver may deliver information such as systemtime information, emergency alert information, etc. to the companiondevice.

FIG. 8 illustrates data processing in a link layer according to anembodiment of the present invention.

The link layer may correspond to a protocol that processes data betweena physical layer and a network layer. Refer to the OSI 7 layer model fora description of each layer. Data processing in the link layer in atransmitter may include a procedure for processing data delivered fromthe network layer (higher layer of the physical layer) and deliveringthe processed data to the physical layer. Data processing in the linklayer in a receiver may include a procedure for processing data from thephysical layer and delivering the processed data to the network layer.The purpose of data processing in the link layer is to process packetsfrom a higher layer into a single format that can be processed in thephysical layer. The purpose of data processing in the link layer is tosecure scalability and flexibility for processing types of input packetsfrom a higher layer, which have not been defined but may be defined inthe future, in broadcast systems. The purpose of data processing in thelink layer is to process input data (input packets: packets deliveredfrom a higher layer of the link layer to the link layer from theviewpoint of the transmitter) such that the input data can beefficiently transmitted. For example, data processing in the link layermay include a procedure for compressing or removing redundantinformation in headers of input packets. Processing in the link layer,defined in a broadcast system according to the present embodiment, maybe referred to as an ATSC link layer protocol (ALP) (a link layerprotocol hereinafter) and packets including data processed through theALP may be referred to as ALP packets.

Referring to the figure showing processing at the transmitter, thehigher layer of the link layer may deliver IP, MPEG2-TS and/or otherpackets to the link layer. The link layer may process data and/orpackets delivered from the higher layer into ALP packets (link layerpackets). During this procedure, data (referred to as media datahereinafter) used for presentation of a service and/or content andsignaling information including information necessary to appropriatelyacquire the data may be generated. The ALP packets may include the mediadata and/or the signaling information. The ALP packets may be generatedin a format that can be processed in the physical layer. Accordingly,the broadcast system may transmit the data/packets delivered from thehigher layer of the link layer from the transmitter to the receiverthrough the physical layer irrespective of the protocol to which thedata/packet conforms.

Referring to the figure showing processing in the receiver, thebroadcast system receives a service signal (a broadcast signal and/or abroadband signal) in the physical layer and extracts one or more ALPpackets including the media data and/or the signaling information. Thebroadcast system may restore the data and/or packets of the higher layerof the link layer in the link layer through a reverse of the dataprocessing procedure performed by the transmitter. The broadcast systemmay process the data and/or packets according to the protocol of thehigher layer and provide a service and/or content to viewers.

Processing in the link layer may include all or part of theaforementioned overhead reduction, IP overhead removal, MPEG2-TSoverhead removal, packet encapsulation, concatenation and segmentationprocesses.

FIG. 9 illustrates an ALP structure and an interface according to anembodiment of the present invention.

As described above, the ALP processes network layer packets such as IPv4and MPEG2-TS packets as input packets. IPv4 is a protocol mainly used incommunication environments and MPEG2-TS is a protocol mainly used inbroadcast environments. As described above, processing in the link layermay provide scalability and flexibility for processing packets based ona third protocol in addition to packets based on the aforementioned twoprotocols. The ALP may specify signaling and packets for link layersignaling. Link layer signaling may include information for mappingbetween a specific channel or multicast (which may be defined as a dataset provided by the broadcast system for purposes in a specific range)and the physical layer. Link layer signaling may include informationnecessary to restore the aforementioned overhead-removed (or compressed)packets in the receiver.

FIG. 10 illustrates a link layer packet format according to anembodiment of the present invention.

The link layer packet may include a header and a payload (payloadincluding data). The header of the link layer packet may include a baseheader, an additional header and/or an optional header. The additionalheader may be included or may not be included in the header of the linklayer packet according to control fields (information) included in thebase header. Presence or absence of the optional header may be indicatedby a flag field (information) of the additional header. A fieldindicating presence of the additional header and the optional header maybe located in the base header.

FIG. 11 illustrates a base header structure of the link layer packetaccording to an embodiment of the present invention. A description willbe given of the header structure.

The structure of the base header is described. The base header withrespect to link layer packet encapsulation has a hierarchical structure.The base header may have a length of 2 bytes, which corresponds to theminimum length of the link layer packet header.

The base header according to an embodiment of the present invention mayinclude a Packet_Type field, a PC field and/or a length field. The baseheader may further include an HM field or an S/C field according toembodiments.

Positions of the fields included in the base header are as shown in thefigure and may be changed in the base header or in the header of thelink layer packet.

FIG. 12 illustrates a syntax of the link layer packet header accordingto an embodiment of the present invention.

The link layer packet header may include a Packet_Type field, aPayload_Configuration (PC) field, a Header_Mode (HM) field, aSegmentation_Concatenation (S/C) field, a length field,Additional_Header_For_Single_Packet,Additional_Header_For_Segmentation_Packet and/orAdditional_Header_For_Concatenation_Packet.

The Packet_Type field is a 3-bit field that indicates the packet type ofinput data before being encapsulated into a link layer packet or theoriginal protocol. IPv4 packets, compressed IP packets, link layersignaling packets and other packets may be encapsulated in this baseheader structure. However, MPEG-2 TS packets may be encapsulated in aspecial structure different from the aforementioned structure accordingto embodiment. When the Packet_Type is “000”, the original data type ofALP packets, “001”, “100” or “111”, corresponds to one of the IPv4packet, compressed IP packet, link layer signaling and an extensionpacket. When MPEG-2 TS packets are encapsulated, the Packet_Type can be“010”. Other Packet_Type field values may be reserved for future use.

The Payload_Configuration (PC) field may be a 1-bit field indicating apayload configuration. A Payload_Configuration (PC) field value of 0 mayindicate that the link layer packet delivers a single input packet andthe next field is Header_Mode. A Payload_Configuration (PC) field valueof 1 may indicate that the link layer packet delivers one or more inputpackets (concatenation) or part of a single large input packet(segmentation) and the next field is Segmentation_Concatenation.

The Header_Mode (HM) field is a 1-bit field indicating that noadditional field is present and the length of the payload of the linklayer packet is less than 2048 bytes when set to 0. This numerical valuemay be changed according to embodiment. A Header_Mode (HM) field valueof 1 may indicate that the additional header for a single packet,defined in the following, follows the length field. In this case, thepayload length may be greater than 2047 bytes and/or option features maybe used (sub-stream identification, header extension, etc.). Thisnumerical value may be changed according to embodiment. The HM field maybe present only when the Payload_Configuration field of the link layerpacket is 0.

The Segmentation_Concatenation (S/C) field may be a 1-bit fieldindicating that the payload delivers segments of the input packet andthe additional header for segmentation, defined in the following,follows the length field when set to 0. A Segmentation_Concatenation(S/C) field of 1 may indicate that the payload delivers two or morecomplete input packets and the additional header for concatenation,defined in the following, follows the length field. The S/C field may bepresent only when the Payload_Configuration field of the ALP packet is1.

The length field may be an 11-bit field indicating 11 least significantbits (LSBs) corresponding to the length, in bytes, of the payloaddelivered by the link layer packet. When the following additional headerincludes a Length_MSB field, the length field is concatenated to theLength_MSB field and becomes LSBs to provide the total length of thepayload. The number of bits of the length field may be changed from 11bits.

The Additional_Header_For_Segmentation_Packet and/or theAdditional_Header_For_Concatenation_Packet will be described in detaillater.

The packet according to an embodiment of the present invention maycorrespond to the following packet types. That is, the packet may be asingle packet having no additional header, a single packet having anadditional header, a segmented packet and a concatenated packet. Morepacket types may be configured according to combinations of theadditional header, the optional header, an additional header forsignaling information and an additional header for type extension, whichwill be described later.

FIG. 13 illustrates a structure and syntax of an additional header for asingle packet according to an embodiment of the present invention.

Various types of additional headers may be present. An additional headerfor a single packet will now be described.

An additional header for a single packet may be present when Header_Mode(HM)=“1”. When the length of the payload of the link layer packet isgreater than 2,047 bytes or an optional field is used, Header_Mode (HM)may be set to 1.

The additional header for a single packet may include a Length_MSBfield, a Sub-stream Identifier Flag (SIF) field, an HEF field, an SIDfield and/or Header_Extension.

The Length_MSB field may be a 5-bit field indicating MSBs of the totalpayload length in bytes in a current link layer packet and isconcatenated to a length field including 11 LSBs to obtain the totalpayload length. Accordingly, the maximum length of a payload that can besignaled is 65,535 bytes. The number of bits of the length field may bechanged from 11 bits. The number of bits of the Length_MSB field may bechanged, and thus a presentable maximum payload length may also bechanged. Each length field may indicate the length of the entire linklayer packet instead of the payload according to embodiment.

The SIF field may be a 1-bit field indicating whether the SID(sub-stream ID) field follows the HEF (Header Extension Flag) field.When the link layer packet does not include the SID, the SIF field maybe set to 0. When the SID follows the HEF field in the link layerpacket, the SIF field may be set to 1. The SID will be described indetail layer.

The HEF field may be a 1-bit field indicating presence of a header forfuture extension when set to 1. An HEF field value of 0 may indicatethat the extension header is not present.

The SID field may be an 8-bit field indicating a sub-stream ID withrespect to the link layer packet. The SID field may be used to filter aspecific packet stream at the link layer level. The SID field mayidentify a sub-stream including link layer packets carrying specificmulticast. Mapping between sub-streams and SID field values may beincluded in link layer signaling and/or higher layer signalinginformation (e.g., SLT and/or SLS). In one embodiment, the SID field mayserve as a service identifier in a single ALP stream. When optionalheader extension is present, the SID field is located between theadditional header and optional header extension. The SID field may beincluded in link layer signaling.

The Header_Extension may include information for extensibility of theadditional header. The Header_Extension may include an Extension_Typefield, an Extension_Length field and/or an Extension_Byte element.

The Extension_Type field may be an 8-bit field indicating the type ofHeader_Extension ( ).

Extension_Length field may be an 8-bit field indicating the byte lengthof Header_Extension ( ), which is counted from the next byte to the lastbyte of Header_Extension ( ).

The Extension_Byte element may indicate the value of Header_Extension ().

FIG. 14 illustrates a structure and syntax of an additional header of alink layer packet in the case of segmentation according to an embodimentof the present invention.

When Segmentation_Concatenation (S/C)=“0”, an additional header(referred to as an additional header for segmentation) for a link layerpacket may be present in the case of segmentation.

The additional header for segmentation may include aSegment_Sequence_Number field, a Last_Segment_Indicator (LSI) field, aSub-stream Identifier Flag (SIF) field, an HEF field, an SID fieldand/or Header_Extension ( ).

The Segment_Sequence_Number field may be a 5-bit unsigned integerindicating a segmentation order delivered by the link layer packet. TheSegment_Sequence_Number field may be set to 0x0 for the link layerpacket delivering the first segment of an input packet. TheSegment_Sequence_Number field may increment for each segment belongingto the input packet to be segmented.

The LSI field may be a 1-bit field indicating that a segment present ina relevant payload is the last segment of the input packet when setto 1. An LSI field value of 0 may indicate that the segment is not thelast segment.

The SIF field may be a 1-bit field indicating that SID follows the HEFfield. When the SID is not present in the link layer packet, the SIFfield may be set to 0. When the SID follows the HEF field in the linklayer packet, the SIF field may be set to 1.

The HEF field may be a 1-bit field indicating that optional headerextension is present after the additional header for future extension ofa link layer header when set to 1. An HEF field value of 0 may indicatethat optional header extension is not present.

Description of the SID field and/or Header_Extension ( ) is replaced bythe above description.

A packet ID field indicating that segments are generated from the sameinput packet may be added according to embodiment. This field may beomitted when segments are not sequentially delivered.

FIG. 15 illustrates a structure and syntax of an additional header of alink layer packet in the case of concatenation according to anembodiment of the present invention.

When Segmentation_Concatenation (S/C)=“1”, an additional header(referred to as an additional header for concatenation hereinafter) of alink layer packet may be present in the case of concatenation.

The additional header for concatenation may include a Length_MSB field,a Count field, an HEF field, a Component_Length field and/orHeader_Extension.

The Length_MSB field may be a 4-bit field indicating MSBs of a payloadlength in bytes in the link layer packet. A maximum length of thepayload becomes 32,767 bytes for concatenation. The numerical value maybe changed as described above.

The count field may indicate the number of packets (input packets)included in the link layer packet. The counter field may be set to 2,corresponding to the number of packets included in the link layerpacket. Accordingly, the maximum number of packets concatenated in thelink layer packet is 9. A method of indicating the number of packets bythe count field may be changed according to embodiments. That is, 1 to 8may be indicated.

The HEF field may be a 1-bit field indicating that optional headerextension is present after the additional header for future extension ofa link layer header when set to 1. An HEF field value of 0 may indicatethat header extension is not present.

The Component_Length field may be a 12-bit field indicating the lengthof each packet in bytes. Component_Length fields are included in thesame order as packets present in a payload except for the last componentpacket. The number of Component_Length fields may be indicated by(Count+1). The same number of Component_Length fields as Count fieldsmay be present according to embodiment. When the link layer headerincludes odd-numbered Component_Length fields, four stuffing bits mayfollow the last Component_Length field. These bits may be set to 0. TheComponent_Length field indicating the length of the last concatenatedinput packet may be present according to embodiment. In this case, thelength of the last concatenated input packet may be indicated by a valueobtained by subtracting the sum of values indicated by respectiveComponent_Length fields from the total payload length.

The aforementioned SID field and/or Header_Extension may be included inthe link layer packet in the form of an optional header.

FIG. 16 illustrates a link layer packet including link layer signalingand syntax of an additional header included therein according to anembodiment of the present invention.

Link layer signaling is included in the link layer packet in thefollowing manner. A signaling packet is identified when the Packet_Typefield of a base header is 100.

The link layer packet may include two additional parts, an additionalheader for signaling information and actual signaling data. The totallength of the link layer signaling packet is indicated by a link layerpacket header.

The additional header for signaling information may include thefollowing fields. Part of the fields may be omitted according toembodiment.

A signaling_Type field may be an 8-bit field indicating a signalingtype.

A signaling_Type_Extension field may be a 16-bit field indicating asignaling attribute. Detailed contents of this field may be defined insignaling specifications.

Signaling_Version may be an 8-bit field indicating a signaling version.

Signaling_Format may be a 2-bit field indicating a data format ofsignaling data. Here, a signaling format may refer to a data format suchas binary, XML, ATSC, table and descriptor.

Signaling_Encoding_Type may be a field indicating anencoding/compression format. This field may indicate whether compressionhas not been performed and whether specific compression has beenperformed. This field may indicate whether signaling information(signaling data) has been encoded through gzip, zip or DEFLATE accordingto the value thereof.

FIG. 17 illustrates a link layer packet including an extended packet(input packet) and a syntax of an additional header included thereinaccording to an embodiment of the present invention.

To provide a mechanism for permitting a nearly unlimited number ofpacket types and additional protocols delivered by a link layer in thefuture, an additional header may be defined. When the Packet_type of thebase header is 111, packet type extension may be used, as describedabove. The figure illustrates a structure of a link layer packetincluding an additional header for type extension to a link layer packetincluding an input packet using a protocol different from theaforementioned protocols, which will be added in the future.

The additional header for type extension may include the followingfields. Part of the fields may be omitted according to embodiment.

An extended_type field may be information, which indicates a protocol orpacket type of an input packet encapsulated into a link layer packet, asa payload. This field may not be used for protocols or packet typeswhich have been defined by the Packet_Type field.

FIG. 18 illustrates a link layer packet including an MPEG2-TS packet anda syntax of a header of the link layer packet according to an embodimentof the present invention.

When the Packet_Type field of the base header is 010, the link layerpacket may include an MPEG2-TS packet. One or more TS packets may beencapsulated in each link layer packet. The number of TS packets may besignaled through a NUMTS field. In this case, a special link layerpacket header format may be used, as described above.

The link layer provides an overhead reduction mechanism for MPEG-2 TSsin order to improve transmission efficiency. A sync byte (0x47) of eachTS packet may be deleted. An option of deleting a null packet and asimilar TS header is provided.

To avoid, unnecessary transmission overhead, a TS null packet (e.g. a TSpacket having PID=0x1FFF) may be deleted. The deleted null packet may berestored using a DNP field in a receiver. The DNP field indicates acount of deleted null packets. A null packet deletion mechanism usingthe DNP field will be described below.

To further improve transmission efficiency, similar headers of MPEG-2 TSpackets may be deleted. When two or more sequential TS packetssequentially increase continuity counter (CC) fields and the headerfields thereof are identical, the header is transmitted once in thefirst packet and other headers are deleted. An HDM field may indicatewhether the header has been deleted. A common TS header deletion processwill be described in detail below. Here, the CC field may be included inthe header of an MPEG2-TS packet. The CC field is information indicatinga sequence number of payloads of TS packets within the range of astream.

When all three overhead reduction mechanisms are executed, overheadreduction may be performed in the order of sync removal, null packetdeletion and common header deletion. The mechanism execution order maybe changed according to embodiment. In addition, some mechanisms may beomitted according to embodiment.

The figure illustrates the header of the link layer packet when MPEG-2TS packet encapsulation is used. When MPEG-2 TS packet encapsulation isused, the header of the link layer packet may include a Packet_Typefield, a number of TS packets (NUMTS) field, an additional header flag(AHF) field, a header deletion mode (HDM) field and/or a deleted nullpackets (DNP) field.

The Packet_Type field may be a 3-bit field indicating a protocol type ofan input packet, as described above. This field may be set to 010 forMPEG-2 TS packet encapsulation.

The NUMTS field may be a 4-bit field indicating the number of TS packetsin the payload of the relevant link layer packet. A maximum of 16 TSpackets may be supported by one link layer packet. NUMTS=0 may indicatethat 16 TS packets are delivered by the payload of the link layerpacket. For all other NUMTS values, the same number of TS packets as theNUMTS value corresponding thereto is recognized. For example, NUMTS=0001indicates that one TS packet is delivered.

The AHF field may indicate presence or absence of the additional header.An AHF field value of 0 indicates absence of the additional header. AnAHF field value of 1 indicates that a 1-byte additional header follows abase header. When a TS packets is deleted or TS header compression isapplied, the AHF field may be set to 1. The additional header for TSpacket encapsulation includes the following two fields and is presentonly when the AHF field is set to 1 in the link layer packet.

The HDM field may be a 1-bit field indicating whether TS header deletionis applicable to the link layer packet. An HDM field value of 1indicates that TS header deletion is applicable and an HDM field valueof 0 indicates that TS header deletion is not applied to the link layerpacket.

The DNP field may be a 7-bit field indicating the number of TS packetsdeleted before the link layer packet. A maximum of 128 null TS packetsmay be deleted. When HDM=0, DNP=0 may indicate deletion of 128 nullpackets. When HDM=1, DNP=0 may indicate that no null packet is deleted.For all other DNP values, the same number of null packets as the DNPvalue corresponding thereto is recognized. For example, DNP=5 refers todeletion of 5 null packets.

The number of bits of each field may be changed and the minimum/maximumvalue indicated by a field may be changed according to the changednumber of bits of the field. The number of bits and the minimum/maximumvalue may be changed by the designer.

A description will be given of sync byte removal.

When a TS packet is encapsulated into a payload of a link layer packet,the sync byte (0x47) may be deleted from the start of the TS packetduring data processing in the link layer. Accordingly, the length of anMPEG2-TS packet encapsulated into a payload of a link layer packet maybecome 187 bytes (instead of the original length of 188 bytes).

FIG. 19 illustrates a process of removing null packets from MPEG2-TSpackets according to an embodiment of the present invention.

Transport stream regulation requires bitrates of the output of amultiplexer of a transmitter and the input of a demultiplexer of areceiver to be uniform with respect to time and requires uniformend-to-end delay. For some transport stream input signals, null packetsmay be present in order to apply a variable bitrate service to streamshaving a uniform bitrate. In this case, a TS null packet (i.e. a TSpacket having PID=0x1FFF) may be removed through link layer processingin order to avoid unnecessary transmission overhead. Such processing isperformed in such a manner that a deleted null packet can be re-insertedinto the original position in a receiver, and thus a uniform bitrate issecured and PCR timestamp update is not needed.

Before generation of a link layer packet, a counter called DNP is resetto 0 and may then be incremented by 1 for each deleted null packet priorto a packet that is not the first null TS packet to be encapsulated intothe payload of the current link layer packet. Thereafter, a group ofcontinuous valid TS packets may be encapsulated into the payload of thecurrent link layer packet and values of fields in the header thereof maybe determined. After the generated link layer packet is inserted into aphysical layer, DNP is reset to 0. When DNP reaches a maximum limit, ifthe next packet is a null packet, the null packet is maintained as avalid packet and encapsulated into the payload of the next link layerpacket. Each link layer packet may include at least one TS packet in thepayload thereof.

The figure illustrates a null packet deletion process when the HDM fieldis “0” and the AHF field is “1”. Referring to the figure, a single nullpacket is deleted prior to transmission of two valid TS packets in thefirst link layer packet. The packet following the valid TS packetsincluded in the first link layer packet may be a null packet.Accordingly, the first link layer packet is completed and the DNPcounter may be reset to 0 for the next link layer packet. In this case,in the header of the first link layer packet, the NUMTS filed may be setto “2” and the DNP field may be set to “1”. In the second link layerpacket, 2 null packets are deleted prior to 4 valid TS packets. In thiscase, the NUMTS field may be set to “4” and the DNP field may be set to“2” in the second link layer packet.

FIG. 20 illustrates a process of deleting headers from MPEG2-TS packetsaccording to an embodiment of the present invention.

TS packet header deletion may be called TS packet header compression.

When two or more sequential TS packets sequentially increase their CCfields and have the same field values in the headers thereof, except forthe CC field, the header of the first TS packet is transmitted and otherheaders may be deleted.

The aforementioned HDM field may indicate whether the header has beendeleted. When the header of a TS packet is deleted, the HDM field may beset to 1.

Referring to the figure, three TS packets have the same header (headerhaving the same fields except for the CC field) as that of the first TSpacket. In this case, the NUMTS field may be set to “4”, the HDM fieldmay be set to “1”, the DNP field may be set to “0” and the AHF field maybe set to “1” in the link layer packet. In a receiver, deleted headersof TS packets other than the first TS packets may be restored using theheader, which is included in the payload of the link layer packet, ofthe first TS packets. The CC fields of the TS packets sequentiallyincrease from the first TS packet such that the headers of the TSpackets are restored.

FIG. 21 illustrates a single packet encapsulation structure of a linklayer according to an embodiment of the present invention.

FIG. 21(a) illustrates an encapsulation structure of a short singlepacket. The short packet may include a Packet_Type field, a PC field, anHM field, a Length field and/or a payload, which have been describedabove.

FIG. 2(b) illustrates an encapsulation structure of a long singlepacket. The long packet may include a Packet_Type field, a PC field, anHM field, a Length field, a Length_MSB field, a Reserved (R) field, anSIF field, an HEF field and/or a payload, which have been describedabove. The long packet may include an SID field and/or an optionalheader.

FIG. 22 illustrates an encapsulation structure of a link layer packet towhich segmentation is applied according to an embodiment of the presentinvention.

FIG. 22(a) illustrates a link layer packet including a first segment ofan input packet. In this case, the link layer packet may include aPacket_Type field, a PC field, an S/C field, a Length field, a Seg_SNfield, an LSI field, an SIF field, an HEF field and/or a payload, whichhave been described above.

FIG. 22(b) illustrates a link layer packet including an intermediatesegment of the input packet. In this case, the link layer packet mayinclude a Packet_Type field, a PC field, an S/C field, a Length field, aSeg_SN field, an LSI field, an SIF field, an HEF field and/or a payload,which have been described above.

FIG. 22(c) illustrates a link layer packet including the last segment ofthe input packet. In this case, the link layer packet may include aPacket_Type field, a PC field, an S/C field, a Length field, a Seg_SNfield, an LSI field, an SIF field, an HEF field and/or a payload, whichhave been described above.

FIG. 23 illustrates an encapsulation structure of a link layer packet towhich concatenation is applied according to an embodiment of the presentinvention.

The link layer packet including a plurality of input packets may includea Packet_Type field, a PC field, an S/C field, a Length field, aLength_MSB field, a Count field, an HEF field, fields (L_1, L_2, . . . ,L_n−1 fields) indicating the respective lengths of the input packetsand/or a payload, which have been described above.

FIG. 24 illustrates the concept of encapsulation of an MPEG2-TS packetin a link layer according to an embodiment of the present invention.

As described above, a link layer packet may include one or more MPEG2-TSpackets. Here, sync bytes of the MPEG2-TS packets may not be included inthe payload of the link layer packet. Referring to the figure, one linklayer packet includes 8 MPEG2-TS packets. A process of encapsulating the8 MPEG2-TS packets into a single link layer packet may include a processof deleting sync bytes for the MPEG2-TS packets. When the sync bytes aredeleted from the MPEG2-TS packets, the link layer packet may carry 187bytes, instead of 188 bytes, for one MPEG2-TS packet. The 8 MPEG2-TSpackets are included in the payload of one link layer packet. In thiscase, the length of the payload of the link layer packet may be187*8=1,496 bytes. The header of the link layer packet is generated bysetting the aforementioned field values in the header of the link layerpacket. Referring to the figure, the Packet_Type field may be set to“010”, the NUMTS field may be set to “1000” and the AHF field may be setto “0”.

According to the present embodiment, throughput of 7 bytes can bereduced through link layer processing, compared to direct transmissionof 8 MPEG2-TS packets to the physical layer.

FIG. 25 illustrates the concept of encapsulation of an MPEG2-TS packetin a link layer using null packet deletion according to an embodiment ofthe present invention.

Link layer processing may include a process of deleting null MPEG2-TSpackets present prior to the first MPEG2-TS packet included in a linklayer packet. In this case, a transmitter may notify a receiver of thenumber of deleted null MPEG2-TS packets using the header of the linklayer packet.

The figure illustrates an embodiment in which a link layer packetincludes 6 MPEG2-TS packets and 2 null MPEG2-TS packets prior to thefirst MPEG2-TS packet in the payload of the link layer packet aredeleted.

For null packet deletion, a broadcast system deletes null packets frominput packets and counts the number of deleted null packets. Thebroadcast system deletes sync bytes included in the MPEG2-TS packets.The broadcast system includes the 6 MPEG2-TS packets in the payload ofthe link layer packet. The broadcast system generates a link layerpacket header suitable for the present embodiment. In the header, thePacket_Type field may be set to “010”, the NUMTS field may be set to“0110”, the AHF field may be set to “1” (this value may indicatepresence of deleted null packets prior to the first MPEG2-TS packetencapsulated into the payload of the link layer packet), the HCM fieldmay be set to “0” and the DNP field may be set to “0000010”.

According to the present embodiment, the broadcast system canappropriately process the MPEG2-TS packets through link layer processingwhile reducing 380 bytes, compared to direct transmission of 8 MPEG2-TSpackets to the physical layer.

FIG. 26 illustrates the concept of encapsulation of an MPEG2-TS packetin the link layer using TS header deletion according to an embodiment ofthe present invention.

Link layer packets may be generated in the link layer by performingadditional compression on MPEG2-TS packets in addition to theaforementioned sync byte deletion and/or null packet deletion.

Referring to the figure, headers of 8 MPEG2-TS packets may includefields having the same values except for the CC field. Link layerprocessing for compressing MPEG2-TS packet headers in the link layer,performed by a broadcast system, may include the following process. Thebroadcast system may group the 8 TS packets (the number of TS packetsmay be changed) including headers having the same field values exceptfor the CC field. The broadcast system may maintain the header of thefirst MPEG2-TS packet, except for the sync bytes, and delete headers ofthe other 7 MPEG2-TS packets. The broadcast system may generate a headerof a link layer packet. In the header of the link layer packet, thePacket_Type field may be set to “010”, the NUMTS field may be set to“0100”, the AHF field may be set to “1”, the HCM field may be set to “1”and the DNP field may be set to “0000000”. The broadcast system maygenerate a link layer packet including part (part remaining after headercompression) of the 8 MPEG2-TS packets. The generated link layer packetmay have a length of 1,477 bytes, which is smaller, by 27 bytes, thanthe length when the 8 MPEG2-TS packets are directly transmitted throughthe physical layer. Accordingly, the present embodiment can decrease thequantity of data transmitted by the broadcast system.

FIG. 27 illustrates a transmission path with respect to context when IPpacket header compression in the link layer is performed according to anembodiment of the present invention.

As described above, the present invention can reduce the quantity ofdata transmitted through a broadcast system by performing IP headercompression when IP packets are delivered to the link layer as inputpackets. A context (or context information) generated during thisprocess may be transmitted from a transmitter to a receiver through apath separated from a path for header-compressed IP packets.

When IP header compression is performed, if the receiver cannot directlyacquire the context at the moment of channel change or power on, thereceiver may not directly restore IP packets (header-compressed IPpackets which may be referred to as “RoHC packets”) for the relevantchannel even if the IP packets are received. Accordingly, the contextmay be transmitted through a path different from a path for theheader-compressed IP packets and the receiver may acquire the contextthrough the path when channels are changed or power is on so as todirectly restore the IP packets according to the present embodiment.

The path through which the context is transmitted may be a path throughwhich signaling information is delivered. For example, when a PLP thatdelivers the signaling information is present, the PLP may deliver thecontext. Alternatively, the context transmission path may bepre-designated such that the receiver may receive the context bydirectly accessing the path.

Through the context transmission path, the same context may berepeatedly transmitted periodically or aperiodically such that receiverscan directly acquire the context at the moment of channel change orpower on since the receivers may have different channel change or poweron timings.

FIG. 28 illustrates a process of acquiring a context in a receiveraccording to an embodiment of the present invention.

As described above, when the context is transmitted through a pathdifferent from a path for a stream carrying IP packets, a receiver mayacquire signaling information first. That is, the receiver may acquirethe context transmitted through a PLP (or DP) that carries the signalinginformation during a procedure for accessing the PLP to obtain thesignaling information. After acquisition of the signaling information,the receiver may select a PLP for acquiring a stream carrying IPpackets. During this procedure, the receiver may obtain the contextprior to acquisition of the stream carrying IP packets. An adaptationmodule of the receiver may detect an IR-DYN packet from a receivedpacket flow (a set of IP packets). The adaptation module may parse astatic chain included in the context. This process is similar to aprocess of acquiring IP packets. IR-DYN packets having the same contextidentifier may be restored to IR packets. A restored RoHC packet flowmay be transmitted to an RoHC restoration unit and restored to IPpackets.

FIG. 29 is a flowchart illustrating a method of generating andprocessing a broadcast signal according to an embodiment of the presentinvention.

A transmitter receives one or more packets from among Internet protocol(IP) packets and MPEG2-TS packets as input packets (JS29010).

The transmitter generates at least one link layer packet including thereceived input packets (JS29020). In generation of the link layerpacket, the transmitter may delete null packets from among the MPEG2-TSpackets, delete sync bytes included in MPEG2-TS packets remaining afterdeletion of the null packets and generate the link layer packetincluding a header and a payload containing the MPEG2-TS packets fromwhich sync bytes have been deleted.

The transmitter generates a broadcast signal including the at least onelink layer packet (JS29030).

The transmitter transmits the broadcast signal (JS29040).

According to an embodiment of the present invention, the header of thelink layer packet may include Packet_Type information that specifies thetype of an input packet included in the payload of the link layer packetand NUMTS information that indicates the number of MPEG2-TS packets fromwhich the sync bytes have been deleted, which are included in thepayload of the link layer packet.

According to an embodiment of the present invention, the header of thelink layer packet may further include DNP information that indicates thenumber of deleted null packets.

According to an embodiment of the present invention, the MPEG2-TSpackets may include a first MPEG2-TS packet, a second MPEG2-TS packetand a third MPEG2-TS packet. The first MPEG2-TS packet may include afirst MPEG2-TS packet header and a first MPEG2-TS packet payload, thesecond MPEG2-TS packet may include a second MPEG2-TS packet header and asecond MPEG2-TS packet payload, and the third MPEG2-TS packet mayinclude a third MPEG2-TS packet header and a third MPEG2-TS packetpayload. The step of generating at least one link layer packet mayinclude a step of deleting the second MPEG2-TS packet header and thethird MPEG2-TS packet header when the second MPEG2-TS packet header andthe third MPEG2-TS packet header include fields having the same valuesas those included in the first MPEG2-TS packet header, except for acontinuity counter (CC) field, and a step of generating a link layerpacket including a link layer packet payload containing the firstMPEG2-TS packet header, the first MPEG2-TS packet payload, the secondMPEG2-TS packet payload and the third MPEG2-TS packet payload, and thelink layer packet header.

According to an embodiment of the present invention, the link layerpacket header may include HDM information that indicates that the secondMPEG2-TS packet header and the third MPEG2-TS packet header have beendeleted.

According to an embodiment of the present invention, the step ofgenerating at least one link layer packet may further include a step ofgenerating link layer signaling information containing information forprocessing the link layer packets and a step of generating a link layersignaling packet including the generated link layer signalinginformation.

According to an embodiment of the present invention, the link layersignaling packet may include signaling type information that specifiesthe type of the link layer signaling information included in the linklayer signaling packet, signaling version information that indicates theversion of the link layer signaling information, signaling formatinformation that specifies the data format of the link layer signalinginformation and signaling encoding type information that specifies anencoding format applied to data of the link layer signaling information.

FIG. 30 illustrates a broadcast system according to an embodiment of thepresent invention.

The broadcast system according to an embodiment of the present inventionincludes a transmitter J30100 and/or a receiver J30200.

The transmitter J30100 may include a data generator J30110, a processorJ30120, a broadcast signal generator J30130 and/or a broadcast signaltransmitter J30140.

The data generator J30110 generates data for broadcast content providedby the broadcast system.

The processor J30120 receives one or more packets from among IP packetsand MPEG2-TS packets as input packets and generates at least one linklayer packet including the received input packets. Here, the processorJ30120 may delete null packets from among MPEG2-TS packets, delete syncbytes included in MPEG2-TS packets remaining after deletion of the nullpackets and generate a link layer packet including a header and apayload containing the MPEG2-TS packets from which sync bytes have beendeleted. The processor J30120 may include a signaling encoder (notshown). The signaling encoder encodes or generates the aforementionedsignaling information. The signaling information includes low levelsignaling, a service list table, service layer signaling, an MPD, an MPtable, copy control information and/or metadata of ISOBMFF, as describedabove.

The broadcast signal generator J30130 generates a broadcast signalincluding the at least one link layer packet.

The broadcast signal transmitter J30140 transmits the broadcast signal.

The receiver J43200 includes a signal receiver J43210, a processorJ43220 and/or a display J43230.

The signal receiver J30210 receives a broadcast signal or a broadbandsignal.

The processor J30220 restores IP packets and/or MPEG2-TS packets thatmay be included in link layer packets by performing processingcorresponding to the aforementioned link layer processing applied to theIP packets and/or MPEG2-TS packets. That is, when headers of IP packetsincluded in link layer packets have been compressed, the processorJ30220 decompresses the compressed headers to restore input packetsinput to a link layer of a transmitting side. When header compression,null packet deletion and/or sync byte deletion have been performed onMPEG2-TS packets included in link layer packets, the processor J30220performs restoration of compressed headers, null packets and sync bytesto restore input packets input to the link layer of the transmittingside. The processor J30220 may decode the signaling information. Theprocessor J30220 processes the signaling information and dataconstituting broadcast content to decode the signaling information anddata into data for media presentation.

The display J30230 presents media using the decoded data.

Modules or units may be processors executing consecutive processesstored in a memory (or a storage unit). The steps described in theaforementioned embodiments can be performed by hardware/processors.Modules/blocks/units described in the above embodiments can operate ashardware/processors. The methods proposed by the present invention canbe executed as code. Such code can be written on a processor-readablestorage medium and thus can be read by a processor provided by anapparatus.

While the embodiments have been described with reference to respectivedrawings for convenience, embodiments may be combined to implement a newembodiment. In addition, designing a computer-readable recording mediumstoring programs for implementing the aforementioned embodiments iswithin the scope of the present invention.

The apparatus and method according to the present invention are notlimited to the configurations and methods of the above-describedembodiments and all or some of the embodiments may be selectivelycombined to obtain various modifications.

The methods proposed by the present invention may be implemented asprocessor-readable code stored in a processor-readable recording mediumincluded in a network device. The processor-readable recording mediumincludes all kinds of recording media storing data readable by aprocessor. Examples of the processor-readable recording medium include aROM, a RAM, a CD-ROM, a magnetic tape, a floppy disk, an optical datastorage device and the like, and implementation as carrier waves such astransmission over the Internet. In addition, the processor-readablerecording medium may be distributed to computer systems connectedthrough a network, stored and executed as code readable in a distributedmanner.

Although the preferred embodiments of the present invention have beendisclosed for illustrative purposes, those skilled in the art willappreciate that various modifications, additions and substitutions arepossible, without departing from the scope and spirit of the inventionas disclosed in the accompanying claims. Such modifications should notbe individually understood from the technical spirit or prospect of thepresent invention.

Both apparatus and method inventions are mentioned in this specificationand descriptions of both the apparatus and method inventions may becomplementarily applied to each other.

Those skilled in the art will appreciate that the present invention maybe carried out in other specific ways than those set forth hereinwithout departing from the spirit and essential characteristics of thepresent invention. Therefore, the scope of the invention should bedetermined by the appended claims and their legal equivalents, not bythe above description, and all changes coming within the meaning andequivalency range of the appended claims are intended to be embracedtherein.

In the specification, both the apparatus invention and the methodinvention are mentioned and description of both the apparatus inventionand the method invention can be applied complementarily.

[Mode for Invention]

Various embodiments have been described in the best mode for carryingout the invention.

INDUSTRIAL APPLICABILITY

The present invention is applied to broadcast signal providing fields.

Various equivalent modifications are possible within the spirit andscope of the present invention, as those skilled in the relevant artwill recognize and appreciate. Accordingly, it is intended that thepresent invention cover the modifications and variations of thisinvention provided they come within the scope of the appended claims andtheir equivalents.

1. A method of generating and processing a broadcast signal, comprising:receiving one or more packets, from among Internet protocol (IP) packetsand MPEG2-TS packets, as input packets; generating one or more linklayer packets including the received input packets, wherein thegenerating of the one or more link layer packets include: deleting nullpackets from among the MPEG2-TS packets, deleting sync bytes included inMPEG2-TS packets remaining after deletion of the null packets, andgenerating a link layer packet including a link layer packet header anda link layer packet payload containing the MPEG2-TS packets from whichthe sync bytes have been deleted; generating a broadcast signalincluding the one or more link layer packets; and transmitting thebroadcast signal.
 2. The method according to claim 1, wherein the linklayer packet header includes Packet_Type information specifying a typeof an input packet included in the link layer packet payload and NUMTSinformation indicating the number of MPEG2-TS packets from which thesync bytes have been deleted, the MPEG2-TS packets being included in thelink layer packet payload.
 3. The method according to claim 2, whereinthe link layer packet header further includes DNP information indicatingthe number of deleted null packets.
 4. The method according to claim 1,wherein the MPEG2-TS packets include a first MPEG2-TS packet, a secondMPEG2-TS packet and a third MPEG2-TS packet, wherein the first MPEG2-TSpacket includes a first MPEG2-TS packet header and a first MPEG2-TSpacket payload, the second MPEG2-TS packet includes a second MPEG2-TSpacket header and a second MPEG2-TS packet payload, and the thirdMPEG2-TS packet includes a third MPEG2-TS packet header and a thirdMPEG2-TS packet payload, wherein the generating of the at least one linklayer packet comprises: deleting the second MPEG2-TS packet header andthe third MPEG2-TS packet header when the second MPEG2-TS packet headerand the third MPEG2-TS packet header include fields having the samevalues as those included in the first MPEG2-TS packet header, except fora continuity counter (CC) field; and generating at least one link layerpacket including a link layer packet payload containing the firstMPEG2-TS packet header, the first MPEG2-TS packet payload, the secondMPEG2-TS packet payload and the third MPEG2-TS packet payload, and thelink layer packet header.
 5. The method according to claim 4, whereinthe link layer packet header includes HDM information indicating thatthe second MPEG2-TS packet header and the third MPEG2-TS packet headerhave been deleted.
 6. The method according to claim 1, wherein thegenerating of the at least one link layer packet further comprises:generating link layer signaling information containing information forprocessing the link layer packets; and generating at least one linklayer signaling packet including the generated link layer signalinginformation.
 7. The method according to claim 6, wherein the link layersignaling packet includes signaling type information specifying a typeof the link layer signaling information included in the link layersignaling packet, signaling version information indicating a version ofthe link layer signaling information, signaling format informationspecifying a data format of the link layer signaling information andsignaling encoding type information specifying an encoding formatapplied to data of the link layer signaling information.
 8. A broadcastsignal transmitter, comprising: a processor configured to receive one ormore packets, from among IP packets and MPEG2-TS packets, as inputpackets and to generate one or more link layer packets including thereceived input packets, wherein the processor deletes null packets fromamong the MPEG2-TS packets, deletes sync bytes included in MPEG2-TSpackets remaining after deletion of the null packets and generates alink layer packet including a link layer packet header and a link layerpacket payload containing the MPEG2-TS packets from which the sync byteshave been deleted; a broadcast signal generation apparatus forgenerating a broadcast signal including the one or more link layerpackets; and a broadcast signal transmission apparatus for transmittingthe broadcast signal.
 9. The broadcast signal transmitter according toclaim 8, wherein the link layer packet header includes Packet_Typeinformation specifying a type of an input packet included in the linklayer packet payload and NUMTS information indicating the number ofMPEG2-TS packets from which the sync bytes have been deleted, theMPEG2-TS packets being included in the link layer packet payload. 10.The broadcast signal transmitter according to claim 9, wherein the linklayer packet header further includes DNP information indicating thenumber of deleted null packets.
 11. The broadcast signal transmitteraccording to claim 8, wherein the MPEG2-TS packets include a firstMPEG2-TS packet, a second MPEG2-TS packet and a third MPEG2-TS packet,wherein the first MPEG2-TS packet includes a first MPEG2-TS packetheader and a first MPEG2-TS packet payload, the second MPEG2-TS packetincludes a second MPEG2-TS packet header and a second MPEG2-TS packetpayload, and the third MPEG2-TS packet includes a third MPEG2-TS packetheader and a third MPEG2-TS packet payload, wherein the processordeletes the second MPEG2-TS packet header and the third MPEG2-TS packetheader when the second MPEG2-TS packet header and the third MPEG2-TSpacket header include fields having the same values as those included inthe first MPEG2-TS packet header, except for a CC field and generates atleast one link layer packet including a link layer packet payloadcontaining the first MPEG2-TS packet header, the first MPEG2-TS packetpayload, the second MPEG2-TS packet payload and the third MPEG2-TSpacket payload, and the link layer packet header.
 12. The broadcastsignal transmitter according to claim 11, wherein the link layer packetheader includes HDM information indicating that the second MPEG2-TSpacket header and the third MPEG2-TS packet header have been deleted.13. The broadcast signal transmitter according to claim 8, wherein theprocessor generates link layer signaling information containinginformation for processing the link layer packets and generates at leastone link layer signaling packet including the generated link layersignaling information.
 14. The broadcast signal transmitter according toclaim 13, wherein the link layer signaling packet includes signalingtype information specifying a type of the link layer signalinginformation included in the link layer signaling packet, signalingversion information indicating a version of the link layer signalinginformation, signaling format information specifying a data format ofthe link layer signaling information and signaling encoding typeinformation specifying an encoding format applied to data of the linklayer signaling information.